Raw Alarms

Raw alarms are unprocessed alarms received by NOBS, the raw alarm server. They may or may not have been forwarded on to Verisae.

Observe uses alarm filtering to validate these alarms, determining whether they are triggered by non-critical issues, like high foot traffic during peak hours.

Columns

The smart table displays the following:

• Site name: Identifies the specific site where the alarm occurred
• Site unit: Refers to the specific unit within the site
• Controller model: Indicates the model of the controller associated with the alarm
• Controller name: Name of the controller generating the alarm
• Product type: Specifies the type of product linked to the alarm
• Alarm definition: Provides a description or definition of the alarm
• Alarm type: Category of the alarm triggered
• Controller list: Lists controllers related to the alarm
• Strategy: Outlines the strategy or approach linked to the alarm
• Serial number: Serial number of the equipment involved in the alarm
• Occurred: Date and time when the alarm occurred
• Cleared: Date and time when the alarm was cleared
• Filtered: Indicates whether the alarm passed through the filtering process
• Date forwarded: Date when the alarm was forwarded to the application
• Date modified: Date when any modification to the alarm data occurred
• Date created: Date when the alarm was initially created

The resulting item list may be exported as an Excel document, tab delimited, or comma delimited.

Create a new alarm, or test alarm, and clear selected alarms selection buttons are located at the bottom of the page.

Search results

The smart table displays search results based on specific criteria:

• Filtered is Yes and the date forwarded is populated: The alarm has entered the main application

• Filtered is No: the client has elected to not allow that alarm to enter the main application

• Filtered is Yes and the date forwarded column is blank: the alarm is in the filtering process